Reject version release
Instructions in the Portal:
-
Click on the object at and then on Reject version release:
Note: In the Portal and Apps, you can perform workflow actions in the following areas using the More actions button:
-
Object formats
-
Properties sidebar
-
Quick navigation
-
Favorites
-
Search results in the Portal search
-
My tasks
Attention: After a version has been rejected, it can no longer be released. The state of the rejected draft is frozen and can no longer be edited. A draft cannot be changed and versioned again until the rejected version is deleted.
-
-
In the Reject version release dialog, enter a rejection reason in the comment field and click Reject version release:
Note: In the Reject version release dialog, Enter rejection reason is a mandatory field and marked with *.
The status of the process is set to Release rejected: The creator of the release workflow gets the task to delete the draft in My Tasks in Current tasks:
-
Click the More actions button at the object
-
Click Delete draft version on the context menu:
Note: In the delivery state, drafts can only be deleted by the creator or by users with administrator rights. See chapter Execution permissions in the standard release workflow.
Instructions in the WebModeller:
-
In the WebModeller, in the model overview, select the process
-
On the context menu, click Further actions | Reject version release:
Attention: After a version has been rejected, it can no longer be released. The state of the rejected draft is frozen and can no longer be edited. A draft cannot be changed and versioned again until the rejected version is deleted.
-
In the Reject version release dialog, enter a rejection reason in the comment field and click Reject version release:
-
In the model overview, select the process again
-
On the context menu, click Further actions | Delete draft version:
Results:
-
The version was deleted. A note about the successful action appears in the bottom right corner:
-
The version no longer appears in the version history.
-
The object exists again in its previous working draft and can be edited again.
-
The release workflow can be started again.